System for a personal wearable micro-server

ABSTRACT

Embodiments include a computer program product for using a biosensor worn by a user to trigger an event and activate a camera worn by the user to begin streaming and/or recording video data. The biosensor trigger also initiates a real time multimedia collaboration session with the user wearing the biosensor and one or more designated parties. Through an interoperability gateway device, a voice communications device of the user is bridged with voice communications devices of the designated parties, and the video data is electronically transmitted to the designated parties. Thus, the designated parties may have real time voice communications among each other and with the user, and the designated parties may also view the video data in real time. Embodiments also determine when an event has ended and deactivates the camera worn by the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/988,865, filed Aug. 10, 2020, entitled “Biosensor-TriggeredCollaboration,” which is a continuation of U.S. application Ser. No.16/557,617, filed Aug. 30, 2019, entitled “System forBiosensor-Triggered Collaboration,” which is a continuation of U.S.application Ser. No. 16/049,590, filed Jul. 30, 2018, entitled“Biosensor-Triggered Multimedia Collaboration,” which is a continuationof U.S. application Ser. No. 15/242,792, filed Aug. 22, 2016, entitled“System and Method for Biosensor-Triggered Multimedia Collaboration,”which is a continuation of allowed U.S. application Ser. No. 14/642,325,filed Mar. 9, 2015, entitled “System and Method for Biosensor-TriggeredMultimedia Collaboration,” all of which are incorporated herein byreference in their entireties.

BACKGROUND Field

The embodiments generally relate to electronic communications amongsecure communities, and more particularly, to providingbiosensor-triggered, real-time video data in multimedia collaborationsessions in and among secure communities including incidentcommunications networks.

Background

Presently, a plethora of disparate communications resources existincluding resources using private wireless communications (e.g., publicsafety and first responder communications networks), public switchednetwork communications resources, public wireless networks, networks ofvideo surveillance devices, private security networks, and the like.Additionally, millions of consumers and public officials are nowequipped with smartphone devices that include multiple communicationsabilities including both voice and video communications.

Often these communications resources cannot communicate with each other.For example, private wireless communication networks, such as those usedby public safety or commercial users, are typically isolated from oneanother and utilize different and often incompatible technologies. Whileinteroperability products are available to interconnect such diversesystems, cooperation among the entities involved is often a barrier tofull and scalable implementation. Thus, first responder communicationsystems exist (e.g., silo-ed communications systems), where control ofthe resources of each organization coupled to the system is controlledby a central administrator or controller, and each organizationproviding resources to the system must relinquish control of itsresources to the central administrator. The organization responsible forthe operation of its radio system(s) may be unable or unwilling to grantcontrol of its resources either to peer organizations or to ahigher-level organization.

U.S. Pat. No. 7,643,445, entitled Interoperable Communications Systemand Method of Use, issued on Jan. 5, 2010, and U.S. Pat. No. 8,320,874,entitled System and Method for Establishing an Incident CommunicationsNetwork, issued on Nov. 27, 2012, both of which are incorporated byreference in their entirety, describe systems and methods for providingan interoperable communications system (“interop system,” also referredto as an Incident Communications Network) including a plurality ofotherwise disjunct or disparate communications systems that addressedthe deficiencies of prior art systems. The '445 and '874 patentsspecifically describe methods for establishing an incidentcommunications network that enables interoperable communications amongcommunications resources controlled by multiple organizations during anincident involving emergency or pre-planned multi-organizationcommunications wherein a communications resource is controlled by anadministrator within an organization.

Additionally, U.S. Pat. No. 8,364,153, entitled Mobile InteroperabilityWorkstation Controller Having Video Capabilities within an IncidentCommunications Network, issued on Jan. 29, 2013, (“Mobile IWC Patent”)which is also incorporated herein by reference in its entirety, extendsthe concepts of the '445 and '874 patents. Namely, the Mobile IWC Patentincludes enhanced video capture and streaming capabilities that areintegrated with incident information and events to facilitate improvedmanagement and analysis of incidents or events in which an incidentcommunications network is employed.

U.S. Pat. No. 8,811,940, entitled Dynamic Asset Marshalling Within anIncident Communications Network, issued on Aug. 19, 2014, (“MarshallingPatent”) which is also incorporated herein by reference in its entirety,extends the concepts of the '445 and '874 patents. Namely, theMarshalling Patent provides systems and methods that marshal resourcesinto an incident communications network based on a variety of factors,such as the type of incident and the type of resource being marshaled.

U.S. Patent Publication 2013/0198517, entitled Enabling Ad Hoc TrustedConnections Among Enclaved Communication Communities, filed on Mar. 13,2013, (“Enclaved Application”) which is also incorporated herein byreference in its entirety, extends the concepts of the '445 and '874patents. Namely, the Enclave Application presents systems and methodsfor dynamic access among secure communities, such as incidentcommunications networks, that enables communication resources of a firstsecure community to securely access and/or utilize communicationresources within other secure communities.

Inadequate Body-Worn Cameras

The use of body worn cameras by law enforcement personnel and soldiersis becoming more common to document events as they occur in the field.In some instances, systems have been devised that enable body-worncameras to record video data and stream the video data to anotherreceiving point such as a control or viewing station. Streaming can beaccomplished over a wireless network connection via a radio transceivercoupled to a body worn video camera.

There are at least three general technical problems with existingbody-worn cameras. First, a user (e.g., a law enforcement officer) mustactivate the body worn camera and users often forget to do so duringchaotic or stressful situations. Second, if the body-worn camera is leftin an active recording state to avoid the first problem, other issuesarise. For example, the practical duration for active recording islimited by the finite camera-based data storage capacity of thebody-worn camera device. When the camera-based data storage capacity isincreased to accommodate the continuous recording state, the size of thebody-worn device likewise increases and becomes less desirable.Alternatively, the camera-based data storage may be overwritten whencapacity is reached, but important video data may be lost. If streamingis employed to offload the video data from the camera-based data storageby transmitting the video data to a different storage, the video datatransmission consumes significant wireless bandwidth thereby resultingin excessive costs especially when utilizing commercial wirelessbroadband services. In addition, continuous recording and/or streamingis power intensive and small batteries in a body-worn camera aretypically insufficient for extended use.

The third general technical problem is that current body-worn camerasare standalone systems and are not connected to, or integrated withcommunications devices typically used in responding situations, such asradios and mobile phone devices. Even when the video data is streamed toa different storage, the video data is electronically transmitted to afixed and pre-determined reception point not accessible by users oftypical communications devices. In the case of a distress situation,voice communication is typically established over a radio channelenabling for example, push to talk (PTT) communications among radio endpoints (e.g., users with PTT mobile units) in the same channel anddispatch communications centers. A first person viewing the video datastreamed from a body-worn camera is not able to speak with the userwearing the body-worn camera. And, a second person that can speak (e.g.,have voice communications established) with the user wearing thebody-worn camera cannot view the video data streamed from the user'sbody-worn camera. When a third person is from a different agency or adifferent department, the third person can neither speak with the userwearing the body-worn camera, nor view video data from the user'sbody-worn camera in the absence of pre-planning and the issuance ofaccess credentials. The various silo-ed communications systems limit theability for personnel to communicate in real time and share video datastreamed from a body-worn camera in a seamless and cohesive manner.

BRIEF SUMMARY OF THE INVENTION

What is needed is a system, method, and computer program product forusing a biosensor worn by a user to trigger an event and activate acamera worn by the user to begin streaming and/or recording video data.The biosensor trigger also initiates a real time multimediacollaboration session with the user wearing the biosensor and one ormore designated parties. Through an interoperability gateway device, avoice communications device of the user is bridged with voicecommunications devices of the designated parties, and the video data iselectronically transmitted to the designated parties. Thus, thedesignated parties may have real time voice communications among eachother and with the user, and the designated parties may also view thevideo data in real time. Embodiments also determine when an event hasended and deactivates the camera worn by the user.

Embodiments include a system, method, and computer medium storage forelectronically receiving a first biometric signal from a biosensor wornby a user, wherein the biosensor is associated with a firstinteroperability workstation (IWS) of a first agency, and electronicallydetermining using the biometric signal, when an event occurs. When anevent occurs, embodiments include electronically transmitting anactivation message to a camera device worn by the user to beginrecording and transmitting video data, and electronically transmittingan event alert to the first IWS. Based on rules, the first IWSestablishes a biosensor-triggered multimedia collaboration sessionincluding one or more first resources under control of the first IWSincluding a voice communication device of the user, and the video datatransmitted by the camera device. In addition, the one or more firstresources receive in real time, the video data transmitted by the cameradevice via an interoperability gateway device and have voicecommunications with the user. Embodiments also include electronicallyreceiving a second biometric signal from the biosensor, andelectronically determining using the second biometric signal, when theevent has ceased. When the event has ceased, embodiments further includeelectronically transmitting a deactivation message to the camera deviceto cease recording video data according to rules, such as a prescribedperiod of time after event cessation.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this specification, illustrate embodiments of the invention andtogether with the description serve to explain the principles of theinvention. In the drawings:

FIG. 1A illustrates a diagram of a system according to an embodiment.

FIG. 1B illustrates a diagram of a system with networked personalwearable micro-servers according to an embodiment.

FIG. 2A illustrates a more detailed block diagram of a system accordingto an embodiment.

FIG. 2B illustrates a more detailed block diagram of a system withnetworked personal wearable micro-servers according to an embodiment.

FIG. 3A is a flow chart of a method for biosensor-triggered multimediacollaboration according to an embodiment.

FIG. 3B is a flow chart of a method for biosensor-triggered multimediacollaboration with networked personal wearable micro-servers accordingto an embodiment.

FIG. 4 is a flow chart of a method for a relay gateway according to anembodiment.

FIG. 5 illustrates deployment of mobile ad-hoc radio-based linkedextensible (MARBLE) units according to an embodiment.

FIG. 6 illustrates a system for a MARBLE unit according to anembodiment.

FIG. 7A illustrates an example of sensor pairing according to anembodiment.

FIG. 7B illustrates an example of offset sensor pairing according to anembodiment.

FIG. 8 is an example system useable to implement embodiments.

FIG. 9 is an example conventional system.

DETAILED DESCRIPTION

Conventional body-worn cameras are standalone systems and are notconnected to, or integrated with communications devices typically usedin responding situations, such as radios and mobile phone devices. FIG.9 is an example conventional system 900. Field personnel 908 of Agency Cmay carry radio communications device 962, body-worn camera 954, andmobile device with broadband data 958 such as a smart phone. Voicecommunication is typically established over a radio channel enabling forexample, push to talk (PTT) communications among radio communicationsdevice 962 and radio communications devices associated other personnelof Agency C 902 in the same channel and dispatch communications centers.Field personnel 908 may also use mobile device with broadband 958 thatutilizes wireless network 980 to establish voice communications withpersonnel of Agency C that may include PTT communications.

When field personnel 908 activates body-worn camera 954, video data frombody-worn camera 954 is recorded and may be forwarded to video datastorage system 970 that is a fixed and pre-determined reception point. Afirst personnel of Agency C that can view the video data in video datastorage system 970 cannot speak with field personnel 908 because voicecommunications have not been established with field personnel 908.Further, a second personnel of Agency C that has established voicecommunications with the field personnel 908 wearing the body-worn camera954 does not have access to video data storage system 970 and thus,cannot view the video data streamed from body-worn camera 954. Inaddition, a third personnel from Agency D 906 can neither speak withfield personnel 908 wearing body-worn camera 954, nor view video datafrom video data storage system 970 from body-worn camera 954 in theabsence of pre-planning and the issuance of access credentials. Thevarious silo-ed communications systems, voice communications (e.g.,radio system 934) and video communications (e.g., video data storagesystem 970), and separate agency system (e.g., Agency D 906communications) limit the ability for personnel to communicate in realtime and share video data streamed from a body-worn camera.

Overview

FIG. 1A illustrates a diagram of a system 100A according to anembodiment. FIG. 1A includes Agency A 102, Agency B 106, and fieldpersonnel 108 that is associated with Agency A, all of which may haveaccess to an Internet Protocol (IP) network 104 which may be a wiredand/or wireless network, and may include any combination of local areanetworks (LANs), wide area networks (WANs), the Internet, a wide areadata communications network, etc. An agency is a secure community thatincludes a collection of communications and/or media resourcesmaintained by an administrator. As mentioned above, the '445 and '874patents describe methods for establishing an incident communicationsnetwork that enables interoperable communications among communicationsresources such as Agency A 102 and Agency B 106, and the EnclavedApplication includes systems and methods for dynamic access among securecommunities such as Agency A 102 and Agency B 106.

Field personnel 108 (e.g., an officer, a first responder, an agent)associated with Agency A (e.g., a police department, a fire department,or the Federal Bureau of Investigations (FBI)), may carry and/or weardevices including but not limited to at least one of body-worn biosensor152, body-worn camera 154, radio communications device 162, mobiledevice with broadband data 158, and personal wearable micro-server 160that may be coupled via a wired or wireless data communications linkand/or personal area network (PAN) 150. The data communications linkand/or PAN 150 may include at least one of a wired interface includingbut not limited to a universal serial bus (USB) or other wiredinterface, or a wireless interface including but not limited to: aBluetooth, Wi-Fi, Zigbee, or other wireless protocol.

For example, field personnel 108 wears a biometric sensor, body-wornbiosensor 152, which monitors his heart rate. Biometric data (e.g., aheart rate) from body-worn biosensor 152, is electronically transmittedover PAN 150 to a software monitoring application, monitoring module156. Monitoring module 156 operates on a small body-worn computingdevice (e.g., personal wearable micro-server 160) or a handheldcomputing device (e.g., mobile device with broadband data 158) that hasinteroperability gateway functions to access IP network 104.Interoperability gateway functions (e.g., community gateway controllerfunctions) are described in the Enclaved Application. Monitoring module156 which is coupled to body-worn biosensor 152 and body-worn camera 154via PAN 150. Monitoring module 156 monitors biometric data outputs(e.g., the heart rate) from body-worn biosensor 152. These biometricdata are electronically interpreted by a set of rules, parameters, oralgorithms that determine whether the biometric data meet or exceed anestablished trigger threshold. In an example, monitoring module 156 isprogrammed such that an activation message is triggered once theofficer's heart rate exceeds 120 beats per minute. Once monitoringmodule 156 receives biometric data (e.g., the heart rate) from body-wornbiosensor 152 via PAN 150, and detects that the heart rate is in excessof 120 beats per minute, monitoring module 156 electronically transmitsthe activation message via PAN 150 to body-worn camera 154 to commencerecording and/or streaming video data. Monitoring module 156 alsoelectronically transmits via an interoperability gateway device, anevent alert message via a wireless network connection over IP network104, to Agency A 102 that is monitoring field personnel 108 (e.g., theofficer). In this example, based on rules, the received event alertmessage initiates a biosensor-triggered multimedia communicationssession. In conjunction with receipt of the event alert message, AgencyA 102 includes one or more agency media resources such as radio,telephone or other voice communication systems in thebiosensor-triggered multimedia communications session. In anotherexample, Agency A 102 invites one or more other media resources inAgency B 106 to join the biosensor-triggered multimedia collaborationsession to become an inter-agency biosensor-triggered multimediacollaboration session. Upon joining the incident collaboration session,interoperability workstations (IWSs) and media and/or communicationsresources in the respective Agency A 102 and Agency B 106 may have voicecommunications with field personnel 108 and also receive the video dataelectronically transmitted via the interoperability gateway device, frombody-worn camera 154.

In an example, monitoring module 156 is programmed such that adeactivation message is triggered once the officer's heart rate dropsbelow 80 beats per minute. Once monitoring module 156 receives biometricdata (e.g., the heart rate) from body-worn biosensor 152 via PAN 150,and detects that the heart rate is below 80 beats per minute, monitoringmodule 156 electronically transmits the deactivation message via PAN 150to body-worn camera 154 to cease recording and/or streaming video data.Monitoring module 156 also electronically transmits via theinteroperability gateway device, a camera deactivated message via awireless network connection over IP network 104, to Agency A 102 that ismonitoring field personnel 108 (e.g., the officer). In this example,based on rules and the received camera deactivated message, Agency A 102may deactivate the biosensor-triggered multimedia communicationssession.

System

FIG. 2A illustrates a detailed block diagram of a system 200A accordingto an embodiment of the invention that includes Agency A 202, Agency B206, field personnel 208, and Internet Protocol (IP) network 204. IPnetwork 204 is substantially the same as IP network 104 of FIG. 1A.

Field Personnel 208

Field personnel 208 may carry and/or wear devices including but notlimited to at least one of body-worn biosensor 252, monitoring module256, body-worn camera 254, radio communications device 262, mobiledevice with broadband data 258, and personal wearable micro-server 260that communicate via PAN 250.

Radio communications device. Radio communications device 262 may be ahand held or portable communication device that communicates with voiceradio network 230.

Mobile device with broadband data. Mobile device with broadband data 258may be a computing device with an operating system that may include butis not limited to, for example, the iOS platform produced by Apple Inc.of Cupertino, Calif., the Android platform produced by Google Inc. ofMountain View, Calif., the Windows platform produced by Microsoft Corp.of Redmond, Wash., the Blackberry platform produced by Blackberry Ltd.of Ontario, Calif., or the open-source Linux platform (e.g., a smartphone). Mobile device with broadband data 258 may includeinteroperability gateway functions that enable bridging and sharing ofdata from field personnel 208's devices in a biosensor-triggeredmultimedia collaboration session. For example, once abiosensor-triggered multimedia collaboration session is established,body-worn camera 254 may stream audio and video data through theinteroperability gateway functions on mobile device with broadband data258 to the biosensor-triggered multimedia collaboration session. Mobiledevice with broadband data 258 may be coupled to IP network 204 using3G/4G LTE network protocols.

Personal area network (PAN). PAN 250 includes a wired and/or a wirelessdata communications link among devices in close proximity. For example,PAN 250 may include at least one of a wired interface including but notlimited to a universal serial bus (USB), or a wireless interfaceincluding but not limited to: a Bluetooth, WiFi, Zigbee, or otherwireless protocol.

Personal wearable micro-server 260. Personal wearable micro-server 260may be a portable mesh capable radio transceiver device that includesinteroperability gateway functions to connect with IP network 204 thatenable bridging and hence sharing of data from field personnel 208'sdevices in a biosensor-triggered multimedia collaboration session.Personal wearable micro-server 260 is mesh capable, and thus includesand runs a mesh network software application to detect, form, and/orjoin a local ad hoc mesh network. In an embodiment, personal wearablemicro-server 260 may include interoperability gateway functions and amesh network software application to perform relay gateway functionsdescribed below in conjunction with FIG. 2B.

Body-worn biosensor. In an embodiment body-worn biosensor 252 mayproduce a biometric signal of at least one of: a respiration rate, aheart rate, a blood pressure, a perspiration rate, an oxygen level, abody temperature, a voltaic skin response, a bioelectric activity (e.g.,EKG, EEG, neuronal probe data), an altitude, a pitch, a yaw, a rotationor other angular movement, a position, a force, a location, anacceleration, a deceleration, or a change in any of the above (e.g., achange in respiration rate, a change in an acceleration, or a change ina voltaic skin response). In an embodiment, field personnel 208 may alsoinclude body-worn or proximate environmental sensors that monitorenvironmental conditions such as an ambient temperature, a wind chill, adew point, a radiation level, a chemical level, a biological agent, asound, a pressure, a humidity level, a precipitation level, an airpollutant, a lightning strike, a terrain, an altitude, a location (e.g.,from a global positioning system (GPS)), or an air quality level.

Body-worn camera. In an embodiment body-worn camera 254 may be activatedand deactivated based on signals electronically received from monitoringmodule 256. A received signal may initiate audio and visual recording aswell as the capture of still images that may be streamed, or stored andforwarded to a transceiver device with interoperability gatewayfunctions (e.g., personal wearable micro-server 260 or mobile devicewith broadband data 258)

Monitoring module. In an embodiment, monitoring module 256 may inferfield personnel 208's distress as well as a stressful situation, aperformance level, a health risk, or a risk of harm from variousbiometric signals detected, measured, and output by one or morebody-worn biosensors coupled to monitoring module 256. Monitoring module256 may be a thin client software application operating on a localcomputing platform which is coupled to a remote server, computing deviceor application service which hosts a monitoring application software(e.g., Administrative module 222 of interoperability workstation (IWS)220). For example, monitoring module 256 may operate on a body-worncomputing platform (e.g., personal wearable micro-server 260), or on amobile computing platform (e.g., mobile device with broadband data 258).

Monitoring module 256 interprets data from one or more sensors eithersingularly or in combination using factors including biosensor thresholdvalues that indicate or infer a condition such as physical orpsychological distress, a medical emergency, or a presence of a hazard.

In an embodiment, monitoring module 256 compares a biometric signal witha trigger threshold rule comprising at least one of: a criteria, aparameter, a static rule, or a dynamic rule to detect when the triggerthreshold rule is exceeded. The trigger threshold rule may include butis not limited to at least one of: a change in a value over time, a rateof change of values over time, correlations with data from a differentbiosensor sensor, correlations with data from an environmental sensor,correlations with data from a GPS system, a health or a fitnesscondition of the user, a condition of other personnel being monitored inproximity to the user, a material rating, a system rating, or a systemlimit.

Monitoring module 256 also interprets output from environmental sensors.Examples of environmental signals include but are not limited to achemical level, a radiation level, a biological agent, a sound, anambient temperature, a pressure, a wind chill, a dew point, a humiditylevel, a precipitation level, an air pollutant level, a lightningstrike, a terrain, an altitude, a location, an air quality level, or achange in any of the above (e.g., a change in a chemical level, a dewpoint, a precipitation level, or a number of lightning strikes).

When one or more conditions are satisfied or a trigger threshold rule isexceeded, monitoring module 256 detects an event and electronicallytransmits an activation message via PAN 250 to body-worn camera 254and/or other cameras coupled to monitoring module 256 to initiate audioand visual recording and to transmit the recordings to a transceiverdevice with interoperability gateway functions (e.g., personal wearablemicro-server 260 or mobile device with broadband data 258) which sendsthe data to one or more interoperable work stations.

In addition, monitoring module 256 electronically transmits an eventalert message substantially at the same time to Agency A 202 viawireless means including interoperability gateway functions to incidentmanagement module 224 of IWS 220 (described below) to indicate that anevent has been detected. The event alert message may include informationincluding but not limited to the identity of the biosensor wearingpersonnel, the biosensor identification, the biosensor data received bymonitoring module 256, transformed data derived or based on thebiosensor data received (e.g., output from body-worn biosensor 252), thelocation of the subject wearing the body-worn biosensor, and otherenvironmental or context information.

For example, an accelerometer may be body-worn biosensor 252 thatrecords and electronically transmits information regarding an unusualacceleration of the personnel wearing the biosensor (field personnel208) indicating a chase, or a deceleration indicating a sudden impactmonitoring module 256. When the body-worn accelerometer electronicallytransmits information indicating a sudden deceleration coupled within anincrease in the heart rate of field personnel 208 exceeding a normallevel, monitoring module 256 may use algorithms (e.g., rules) to inferthat an accident has occurred, or a sudden vehicle stop occurredfollowed by a foot chase or other strenuous physical activity,especially when coupled with location information such as a body-wornGPS unit. With location information over time, monitoring module 256 mayuse algorithms to infer whether field personnel 208 may be incapacitatedby a lack of movement, or that a foot chase is occurring based onchanging location information over time that shows movement at anextrapolated rate within a human running pace rate. Further, ifbiometric signals from the body-worn accelerometer shows furtheraccelerating and decelerating movements, the monitoring module 256 mayinfer that a possible physical struggle or altercation is occurring.

Sample Rule. Below is an example of a trigger threshold rule.

-   -   IF Personnel 208's accelerometer exceeds −3.0 g at time t    -   AND IF Personnel 208's heart rate monitor values exceeds the        value 120 bpm within 3 seconds prior or 60 seconds after time t,        THEN send Event Alert message to interoperability workstation    -   WHERE the Event Alert message shall contain Wearer ID, Event ID        Code and Latitude and Longitude.

The Event Alert message is electronically transmitted to the associatedor designated IWS, IWS 220, by monitoring module 256 via a routinginteroperability gateway coupled to the monitoring module 256 based uponrules which are programmed into monitoring module 256 or which arereceived from administrative module 222. The Event Alert message mayalso be electronically transmitted via a communications network (e.g.,PAN 250) to one or more other computing clients such as smartphones(e.g., mobile device with broadband data 258) where the Event Alertmessage may be displayed through the computing client application GUI.

In an embodiment, monitoring module 256 may include rules and parametersor be coupled to an automated messaging module (not shown) whichcontains rules and parameters that electronically transmit advisorymessages to the field personnel being monitored. An advisory message maybe an audio and/or visual message that includes information such aswarnings or status updates regarding body-worn biosensor 252 signals,other biosensor signals, and/or environmental sensor signals, includingchanges in sensor signals. Advisory messages may be based on the sameparameters and rules as Event Alerts or use different threshold values.Advisory messages may be advisory and/or include a user action prompt.For example, an advisory message may indicate that an event alertcondition is detected and an emergency incident will be reported unlessfield personnel 208 declines within a specified time frame, fieldpersonnel 208 may select to electronically transmit an event alertmessage. Field users may interact with monitoring module 256 via a GUIdisplayed on a local computing device, or through a voice interactioninterface, or a gesture recognition interface.

Agency A 202

Agency A 202 includes an interoperability workstation (IWS) 220 asdescribed in the '445 and '874 patents; IWS 220 controls the followingresources: radio system 234, telephone system 226, and mobile PTT module228. Agency A 202 also includes IWS 242 that controls othercommunication system 244 which may be a proprietary voice communicationsystem. Gateway device 238 determines whether to grant a request toaccess Agency A 202 as described in the Enclaved Application. Local orWide Area IP network 232 may be a wired and/or wireless network, and maybe any combination of LANs, WANS, etc.

Radio system. Radio system 234 includes voice radio network 230 and IPradio gateway 236. Voice radio network 230 includes antennas and baseconsoles that utilize one or more communications channels including butnot limited to Very High Frequency (VHF) and Ultra High Frequency (UHF).IP radio gateway 236 is equivalent to a radio network interfacecontroller (RNIC) as described in the '445 and '874 patents. IP radiogateway 236 responds to commands from IWS 220 for coupling voice radionetwork 230 to a biosensor-triggered multimedia collaboration session,for example.

IWS. IWS 220 includes administrative module 222 and incident managementmodule 224.

Administrative module. Administrative module 222 may include a softwareapplication running on a server or computing device coupled to IWS 220.Administrative module 222 may be coupled to an application database oran external database resource such as a directory. Administrative module222 enables an operator or administrator to manage biosensors (e.g.,body-worn biosensor 252) and/or environmental sensors, as well as toestablish trigger threshold rules that include but are not limited to anestablished criteria, a parameter, a static rule, or a dynamic rule. Thesensors are registered with administrative module 222 and are assigned aunique identification which may be based on but not limited to at leastone unique identifier such as: a sensor machine address, a serialnumber, an encryption key, an electronic serial number, a telephonenumber, or an IP address. The sensor ID may be further associated with aunique identification of an individual wearing the sensor (e.g.,body-worn biosensor 252) or an individual in proximity to the sensor,where the individual's unique identifier may include but is not limitedto at least one of: a name, an agency name, a department ID, an employeeID number, an operator number, a team ID, a badge number, or a socialsecurity number. Administrative module 222 rules or parameters may beunique for each person or each sensor associated with a person, or maybe the same for all persons or subset of persons wearing the samefunctional type of sensor. For example, field personnel 208 may beassigned a threshold parameter of 120 beats per minute for a heart ratemonitor and field personnel 212 may be assigned a threshold parameter of140 beats per minute for a heart rate monitor.

Administrative module 222 may be centrally provisioned at IWS 220 andthen trigger threshold rules associated with field personnel 208 areelectronically transmitted and stored by monitoring module 256.Alternatively, trigger threshold rules may be provisioned by the personassociated with or wearing the monitored sensor. For example, fieldpersonnel 208 may set trigger threshold rules through a GUI ofmonitoring module 256. In an embodiment, trigger threshold rules includea combination of rules provisioned centrally by IWS 220 and rulesprovisioned by field personnel 208 associated with the sensor.

Administrative module 222 may be coupled with one or more directoriesand databases of other systems and software applications (not shown)which contain, maintain, and update user identification, communicationsand media asset identification, routing, addressing and otherinformation. Administrative module 222 may utilize data in the one ormore directories singly or in combination, and may transform and storedata in an administrative module directory or database (not shown).

Incident management module. Incident management module 224 may be a partof or coupled to administrative module 222, and may include a softwareapplication running on a server or computing device coupled to IWS 220.When incident management module 224 receives and processes event alertmessages from monitor module 256, incident management module 224initiates a biosensor-triggered multimedia collaboration with one ormore designated IWSs, bridges resources, and may invite resources fromone or more partner agencies to join the biosensor-triggered multimediacollaboration session, or may exclude a partner agency from thebiosensor-triggered multimedia collaboration session.

Agency B 206

Agency B 206 may include similar functionality as described in Agency A.

Method

FIG. 3A is a flow chart of a method 300A for biosensor-triggeredmultimedia collaboration according to an embodiment. For ease ofdiscussion and without limitation, FIG. 3A will be described withreference to elements from FIG. 1A and FIG. 2A.

Method 300A begins and at step 305. At step 305, body-worn biosensor 252collects and electronically transmits biometric output to monitoringmodule 256. Method 300A proceeds to step 310.

At step 310, monitoring module 256 receives the biometric output signalsand determines if an event has occurred. Method 300A proceeds to step315.

At step 315, a determination is made whether an event was detected(e.g., recently from step 310 or previously detected and still exists).When an event is detected, method 300A proceeds to step 320 and step 330at substantially the same time. When an event is not detected, method300A proceeds to step 317.

At step 320, body-worn camera 254 electronically receives a controlmessage from monitoring module 256, and begins recording and/orstreaming data. Method 300A proceeds to step 325.

At step 325, body-worn camera 254 streams data via PAN 250 through ainteroperability gateway function to bridge the streamed data to thebiosensor-triggered multimedia collaboration session. As shown in FIG.2A, mobile device with broadband data 258 and personal wearablemicro-server 260 may include the interoperability gateway function.Method 300A returns to step 310.

Returning to step 330, IWS 220 receives an event alert message frommonitoring module 256 and initiates a biosensor-triggered multimediacollaboration session. For example, incident management module 224 ofIWS 220 initiates a biosensor-triggered multimedia collaboration sessionby electronically transmitting a command message to one or moredesignated IWSs. The '445 and '874 patents described initiating aninteroperable network or an incident communications network, and theMarshalling Patent describes systems and methods to marshal resourcesinto an incident communications network based on a variety of factors,such as the type of incident and the type of resource being marshaled.Method 300A proceeds to step 335.

At step 335 a determination is made based on predetermined static rulesor dynamic rules whether IWS 220, IWS 242, or Agency B 206 has mediaand/or communications resources to bridge to the biosensor-triggeredmultimedia collaboration session. Method 300A proceeds to step 340 whenIWS 220 has resources to bridge. Method 300A proceeds to step 345 whenIWS 242 has resources to bridge. And, method 300A proceeds to step 355when Agency B has media and/or communications resources to bridge. WhenIWS 220 has resources to bridge, method 300A proceeds to step 340.

At step 340, IWS 220 bridges one or more media and/or communicationsresources that IWS 220 controls to the biosensor-triggered multimediacollaboration session. For example, at substantially the same time orafter the biosensor-triggered multimedia collaboration session isinitiated, incident management module 224 of IWS 220 electronicallytransmits one or more command messages to couple or bridge certaincommunications and media resources under control of IWS 220 to thebiosensor-triggered multimedia collaboration session. Thesecommunications and media resources automatically include body-worncamera 254 of field personnel 208 from which the event alert messageoriginated, radio communications device 262, mobile device withbroadband data 258 (e.g., smartphone PPT talk group or emergency voicechannel). Once bridged, multiple personnel, invited to thebiosensor-triggered multimedia collaboration session may both view thevideo data streamed from body-worn camera 254 and have real time voicecommunications with field personnel 208. For example, other personnel ofAgency A 202 invited to the biosensor-triggered multimedia collaborationsession using radio system 234 for voice communications may view thevideo data streamed from body-worn camera 254 on a GUI of IWS 220 andspeak to field personnel 208 via their radio communications device.

Other media and/or communications resources may be bridged viapre-determined assignment or dynamic determination. The MarshallingPatent describes methods for marshaling resources into an incidentcommunications network. In this application, dynamic determinations arebased upon dynamic rules within incident management module 224 usingvarious known or accessible parameters to determine the relevancy ofassets to be included in the biosensor-triggered multimediacollaboration session. These parameters may include but are not limitedto: resources that are in geographic proximity to the subject from whichthe event alert message originated (e.g., a body-worn camera worn byfield personnel 212 in proximity to field personnel 208), the identityof the subject associated with a wearable sensor, or various assetsassociated with the subject including but not limited to: a unique userID associated with a Push to Talk Client operating on a mobile phone, aradio unit identifier associated with the subject, or a telephone numberassociated with the subject. Additional parameters may include othermedia and/or communication resources including but not limited toradios, mobile phones, telephones, video cameras and information systemsand/or services that are based on criteria including but not limited torelevant departments, working groups, task groups, divisions, functions,expertise, skills, credentials, or positions. For example, a dynamicrule may result in a body-worn camera and a radio communications deviceof other field personnel in proximity to field personnel 208, beingbridged into the biosensor-triggered multimedia collaboration session.Method 300A returns to step 310.

Returning to step 345, IWS 242 receives an invitation from IWS 220 tojoin the biosensor-triggered multimedia collaboration session. IWS 242determines whether to join and bridge resources that IWS 242 controls tothe session. Method 300A proceeds to step 350.

At step 350, IWS 242 electronically transmits an acceptance to join andmay bridge other communication system 244 to the biosensor-triggeredmultimedia collaboration session after joining the session. Method 300Aproceeds to step 365.

At step 365, IWS 220 receives the acceptance from IWS 242 and adds IWS242 to the biosensor-triggered multimedia collaboration session. Method300A returns to step 310.

Returning to step 355, Agency B 206 receives an invitation to join thebiosensor-triggered multimedia collaboration session from IWS 220. Forexample, at substantially the same time or after the initiation of thebiosensor-triggered multimedia collaboration session, incidentmanagement module 224 electronically transmits command messages toinvite IWSs from other partner agencies (e.g., Agency B 206) with whomsecure communications have been established. An example of dynamicaccess among secure communities is described in the EnclavedApplication. The invitation may be automatically transmitted. In anembodiment, the invitation may be presented in the form of a visualsuggestion on a GUI of IWS 220, coupled with a user selectable item toselectively invite the suggested agency resource or alternatively, toselectively exclude a suggested agency resource. Agency B 206 determineswhether to join and bridge resources that Agency B 206 controls to thesession. Once bridged, multiple personnel, from Agencies A 202 and B 206invited to the biosensor-triggered multimedia collaboration session mayboth view the video data streamed from body-worn camera 254 and havereal time voice communications with field personnel 208. Method 300Aproceeds to step 360.

At step 360, Agency B 206 electronically transmits an acceptance to joinand may bridge the resources that Agency B 206 controls after joiningthe session. Method 300A returns to step 365.

Returning to step 315, when monitoring module 256 determines that anevent is not detected, method 300A proceeds to step 317.

At step 317, a determination is made whether body-worn camera 254 waspreviously activated (e.g., body-worn camera 254 is recording). Whenbody-worn camera 254 was not previously activated, method 300A returnsto step 310. When body-worn camera 254 was previously activated,monitoring module 256 electronically transmits a control message via PAN250 to body-worn camera 254 to stop recording. In addition, monitoringmodule 256 electronically transmits an event-ended message to IWS 220 atsubstantially the same time. Method 300A proceeds to step 370 and step375.

At step 370, body-worn camera 254 receives the control message and stopsrecording data. Method 300A ends.

Proceeding to step 375, IWS 220 electronically receives the event-endedmessage and determines based on static and/or dynamic rules whether tocease the biosensor-triggered multimedia collaboration session. When IWS220 determines to continue the biosensor-triggered multimediacollaboration session (e.g., not to cease the session), method 300Areturns to step 310. For example, more than one event alert may havebeen received and more than one body-worn camera is active. Whenbody-worn camera 254 stops recording, other body-worn cameras, mediadevices, and/or communications devices may be actively engaged in thebiosensor-triggered multimedia collaboration session. When IWS 220 hasnot received an event-ended message associated with each event alert,method 300B returns to step 310. When IWS 220 determines to end thebiosensor-triggered multimedia collaboration session, method 300Aproceeds to step 385.

At step 385, IWS 220 ends the biosensor-triggered multimediacollaboration session and method 300A ends.

Networked Personal Wearable Micro-Servers & Relay Gateway Systems

In an embodiment, a personal wearable micro-server may be connected ornetworked with one or more personal wearable micro-servers. FIG. 1Billustrates a diagram of a system 100B with networked personal wearablemicro-servers according to an embodiment. System 100B includes theelements of system 100A of FIG. 1A and the following additionalelements: local ad hoc mesh network 110, field personnel 112, and fieldpersonnel 113, both of which are associated with Agency A that aresimilarly equipped as field personnel 108. For example, body-wornbiosensor 153, body-worn camera 155, monitoring module 157, mobiledevice with broadband data 159, and PAN 151 of field personnel 112 areequivalent to the functions of body-worn biosensor 152, body-worn camera154, monitoring module 156, mobile device with broadband data 158, andPAN 150 of field personnel 108. Although not shown, field personnel 113includes elements similar to field personnel 112.

In an example, field personnel 108, 112, and 113 may communicate amongthemselves via networked personal wearable micro-servers that form alocal ad hoc infrastructure such as local ad hoc mesh network 110. Fieldpersonnel 108, 112 and 113 may be coupled to local ad hoc mesh network110 via a personal wearable micro-server 160 or 161 running a meshnetwork software application (e.g., 160 and 161 are mesh-capable). Forexample, field personnel 108, 112, and 113 may be first responders thatenter a building that has minimal or no wireless access infrastructure.Field personnel 108, 112, and 113 may communicate among themselves withrespective mobile devices with broadband data 158 and 159 utilizing theradio transceiver functions of mesh-capable personal wearablemicro-server 160 or 161 over local ad hoc mesh network 110.

In an embodiment, a mesh-capable personal wearable micro-server thatalso has interoperability gateway functions may serve as a relay gatewayfor one or more mesh-capable personal wearable micro-servers that arecoupled to a local ad hoc mesh network and do not have interoperabilitygateway functions. For example, personal wearable micro-server 160 maybe a relay gateway for personal wearable micro-servers 161 coupled tolocal ad hoc mesh network 110 so that field personnel 112 and 113 (thatwould otherwise not have access to a wide area data communicationsnetwork, e.g., IP network 104) may communicate with Agency A 102 orother parties over IP network 104 via personal wearable micro-server160, a relay gateway that transmits communications accordingly. In anexample, field personnel 108, 112, and 113 may enter a building that hasminimal or no wireless access infrastructure, and communicate amongthemselves and Agency A 102 with respective mobile devices (e.g., mobiledevices with broadband data 158 and 159). For example, a communicationfrom field personnel 112 to Agency A 102 may traverse from mobile devicewith broadband data 159, PAN 151, personal wearable micro-server 161,local ad hoc mesh network 110, personal wearable micro-server 160, andIP network 104 to reach Agency A 102.

In an embodiment, when two or more personal wearable micro-servers arenetworked and one of the two or more personal wearable micro-servers isa relay gateway, a device associated with the relay gateway may performanalogous functions for a failed device associated with a personalwearable micro-server of the two or more networked personal wearablemicro-servers. For example, personal wearable micro-server 160 andpersonal wearable micro-server 161 may be networked via local ad hocmesh network 110, and a relay gateway (e.g., personal wearablemicro-server 160) is established. If monitoring module 157 of fieldpersonnel 112 fails based on certain parameters (e.g., an applicationfails or the device on which monitoring module 157 resides has a lowpower source condition or fails), monitoring module 156 associated withthe relay gateway (e.g., personal wearable micro-server 160) may providethe monitoring module functions formerly provided by monitoring module157, for field personnel 112.

FIG. 2B illustrates a more detailed block diagram of a system 200B withnetworked personal wearable micro-servers according to an embodiment ofthe invention. System 200B includes the elements of system 200A of FIG.2A and the following additional elements: local ad hoc mesh network 210,field personnel 212, and field personnel 213 that correspond with theelements of FIG. 1B: local ad hoc mesh network 110, field personnel 112,and field personnel 113. In an example, field personnel 212 (and 213)are substantially similar to field personnel 208, but withoutnecessarily having their own interoperability gateway functions (e.g.,no direct access to IP network 204).

Personal wearable micro-server device without interoperability gatewayfunction. In an embodiment, field personnel 212 includes personalwearable micro-server device 261 that includes a mesh network softwareapplication and radio transceiver functions. Personal wearablemicro-server device 261 is a portable mesh-capable radio transceiverdevice capable of detecting other portable mesh-capable radiotransceiver devices, as well as detecting, forming, and/or joining alocal ad hoc mesh network coupled to other personal wearablemicro-server devices running a mesh network software application (e.g.,personal wearable micro-server 260 or a personal wearable micro-server261 of field personnel 213 that is not shown). However, personalwearable micro-server device 261 may not have interoperability gatewayfunctions to access a wide area network (e.g., IP network 204).

Body-worn biosensor 253, body-worn camera 255, monitoring module 257,and PAN 251 of field personnel 212, are equivalent to the functions ofbody-worn biosensor 252, body-worn camera 254, monitoring module 256,and PAN 250 of field personnel 208.

Local ad hoc mesh network. Local ad hoc mesh network 210 is aninfrastructure network that uses but is not limited to at least one of aWi-Fi, Bluetooth or other wireless communication protocol to couple apersonal wearable micro-server (e.g., personal wearable micro-server260) to another personal wearable micro-server (e.g., personal wearablemicro-server 261).

Relay Gateway System. Personal wearable micro-server 260 is a portablemesh-capable personal wearable micro-server that also hasinteroperability gateway functions. Personal wearable micro-server 260may serve as a relay gateway for one or more mesh-capable personalwearable micro-servers that are coupled to a local ad hoc mesh networkand do not have interoperability gateway functions (e.g., personalwearable micro-server 161).

Relay Gateway Method

FIG. 4 is a flow chart of a method 400 for a relay gateway according toan embodiment. For ease of discussion and without limitation, FIG. 4will be described with reference to elements from FIG. 1B and FIG. 2B.For example, method 400 describes a method for a relay gateway system(e.g., personal wearable micro-server 260), a portable mesh-capableradio transceiver (e.g., a mesh endpoint) with interoperability gatewayfunctions running a mesh network software application to establish alocal ad hoc network infrastructure (e.g., local ad hoc mesh network210) with other personal wearable micro-servers (e.g., personal wearablemicro-server 261). The relay gateway system (e.g., personal wearablemicro-server 260) and/or other personal wearable micro-servers may becoupled to a PAN.

Method 400 begins. At step 405. Method 400 detects at least one othermesh endpoint that is also running a mesh network software application(e.g., personal wearable micro-server 260 and/or 261) that may becoupled to a respective different PAN, and exchanges information withthe at least one mesh endpoint to establish a local ad hocinfrastructure network (e.g., local ad hoc mesh network 210). Althoughnot shown, field personnel 213 may include a mesh endpoint such aspersonal wearable micro-server 261 or personal wearable micro-server260, and may be coupled to a PAN similar to field personnel 212 or 208.Method 400 proceeds to step 410.

At step 410, a determination is made whether the at least one meshendpoint has connectivity to a wide area network (e.g., IP Network 204)which may be coupled to an administrative module (e.g., administrativemodule 222). If the at least one mesh endpoint does not haveconnectivity to a wide area network, then method 400 proceeds to step415. If the at least one mesh endpoint has connectivity to a wide areanetwork, then method 400 proceeds to step 420.

At step 415, method 400 designates the relay gateway system (e.g.,personal wearable micro-server 260) to perform relay gateway functionsfor the at least one mesh endpoint (e.g., personal wearable micro-server261) coupled to the local ad hoc infrastructure network (e.g., local adhoc mesh network 210). For example, personal wearable micro-server 260electronically transmits communications from personal wearablemicro-server 261 coupled to local ad hoc mesh network 210, to adestination via IP network 204. Method 400 ends.

Returning to step 420, a relay gateway system (e.g., personal wearablemicro-server 260), exchanges administrative messages with the at leastone mesh endpoint with connectivity to a wide area network (e.g., adifferent relay gateway system not shown) and dynamically determineswhich is designated to perform the relay gateway functions for thenetworked personal wearable micro-servers. For example, field personnel213 may also have a relay gateway system equivalent to personal wearablemicro-server 260. In an embodiment, the dynamic determination may bebased on but is not limited to at least one of a signal strength, aprocessor speed, a bandwidth throughput, a relative number oftransmission links to peers, or a battery power of the at least one meshendpoint. Method 400 proceeds to step 425.

At step 425, a determination is made whether the at least one meshendpoint with connectivity to a wide area network (e.g., the differentrelay gateway system) is designated as the relay gateway for thenetworked personal wearable micro-servers. When the at least one meshend point with connectivity to a wide area network is not designated asthe relay gateway, method 400 proceeds to step 415 as described above.When the at least one mesh endpoint with connectivity to a wide areanetwork is designated as the relay gateway, method 400 stores the atleast one mesh endpoint with connectivity to a wide area networkinformation accordingly and method 400 ends.

Once the relay gateway (e.g., personal wearable micro-server 260) andthe local ad hoc infrastructure network (e.g., local ad hoc mesh network210) are established, a device associated with the relay gateway mayperform analogous functions for a failed device associated with apersonal wearable micro-server coupled to the local ad hocinfrastructure network. For example, monitoring module 256 associatedwith relay gateway personal wearable micro-server 260 may be configuredto perform monitoring module 257 functions associated with personalwearable micro-server 261. For example, when monitoring module 257fails, administrative module 222 may electronically receive anotification. Administrative module 222 may electronically transmit atleast one of the trigger threshold rules or administrative informationof the devices (e.g., body-worn biosensor 253, body-worn camera 255)associated with failed monitoring module 257 to monitoring module 256.Thus, signals from body-worn biosensor 253 may be electronicallytransmitted over PAN 251 to personal wearable micro-server 261, overlocal ad hoc mesh network 210 to personal wearable micro-server 260, andto monitoring module 256 via PAN 250. Monitoring module 256 receives thebiometric signals and determines if an event exists. Monitoring module256 may also receive environmental signals from field personnel 212 anddetermine based on rules whether a combination of biometric signals andenvironmental signals determines if an event exists. Many othercombinations are possible. If an event is determined to exist,monitoring module 256 may electronically transmit a signal to activatebody-worn camera 255 and a signal to Agency A 202 to initiate abiosensor-triggered multimedia collaboration session to be shared withfield personnel 208, or join an existing biosensor-triggered multimediacollaboration session already established by monitoring module 256. Inan embodiment, monitoring module 256 electronically transmits a signalto Agency A 202 to establish a second biosensor-triggered multimediacollaboration session different than one associated with field personnel208.

Networked Personal Wearable Micro-Servers Method

FIG. 3B is a flow chart of a method 300B for biosensor-triggeredmultimedia collaboration with networked personal wearable micro-serversaccording to an embodiment. In this example, monitoring module 256 isconfigured to also perform the functions of a failed monitoring module257. For ease of discussion and without limitation, FIG. 3B will bedescribed with reference to elements from FIG. 1B and FIG. 2B. Method300B is similar to method 300A described in FIG. 3A, and also includesbody-worn biosensor 253 and body-worn camera 255 of field personnel 212.

Method 300B begins and at step 305. At step 305, body-worn biosensors252 and 253 collect and electronically transmit biometric output tomonitoring module 256. Method 300B proceeds to step 310.

At step 310, monitoring module 256 receives the biometric output signalsand determines if an event has occurred. Monitoring module 256 may alsoreceive environmental measurements or signals from field personnel 212.Method 300B proceeds to step 315.

At step 315, a determination is made whether an event was detected(e.g., recently from step 310 or previously detected and still exists).When an event was detected, method 300B proceeds to step 320 and step330 at substantially the same time. When an event was not detected,method 300B proceeds to step 317.

At step 320, body-worn camera 254 and/or body-worn camera 255electronically receive a control message from monitoring module 256, andbegin recording and/or streaming data. Method 300B proceeds to step 325.

At step 325, body-worn camera 254 streams data via PAN 250 through ainteroperability gateway function to bridge the streamed data to thebiosensor-triggered multimedia collaboration session. As shown in FIG.2B, mobile device with broadband data 258 and personal wearablemicro-server 260 may include the interoperability gateway function.Method 300B returns to step 310. When activated, body-worn camera 255streams data via PAN 251 to personal wearable micro-server 261, overlocal ad hoc mesh network 210 to personal wearable micro-server 260, tothe biosensor-triggered multimedia collaboration session shared withfield personnel 208 or a second biosensor-triggered multimediacollaboration session that is established.

Returning to step 330, IWS 220 receives an event alert message frommonitoring module 256 and initiates a biosensor-triggered multimediacollaboration session. For example, incident management module 224 ofIWS 220 initiates a biosensor-triggered multimedia collaboration sessionby electronically transmitting a command message to one or moredesignated IWSs. Method 300B proceeds to step 335. In an embodiment, IWS220 receives an event alert message from monitoring module 256 andenables the video data streamed from body-worn camera 255 to join theestablished biosensor-triggered multimedia collaboration session. In anembodiment, IWS 220 receives an event alert message from monitoringmodule 256 and establishes a second biosensor-triggered multimediacollaboration session that would include the video data streamed frombody-worn camera 255. In an example, the video data streamed frombody-worn camera 255 may be included in one or more biosensor-triggeredmultimedia collaboration sessions.

At step 335 a determination is made based on predetermined static rulesor dynamic rules (that may include information regarding field personnel208 and/or 212) whether IWS 220, IWS 242, or Agency B 206 has mediaand/or communications resources to bridge to the biosensor-triggeredmultimedia collaboration session. Method 300B proceeds to step 340 whenIWS 220 has resources to bridge. Method 300B proceeds to step 345 whenIWS 242 has resources to bridge. And, method 300B proceeds to step 355when Agency B has media and/or communications resources to bridge. WhenIWS 220 has resources to bridge, method 300B proceeds to step 340.

At step 340, IWS 220 bridges one or more media and/or communicationsresources that IWS 220 controls to the biosensor-triggered multimediacollaboration session. For example, at substantially the same time orafter the biosensor-triggered multimedia collaboration session isinitiated, incident management module 224 of IWS 220 electronicallytransmits one or more command messages to couple or bridge certaincommunications and media resources under control of IWS 220 to thebiosensor-triggered multimedia collaboration session. Thesecommunications and media resources automatically include body-worncamera 254 of field personnel 208 and/or body-worn camera 255 of fieldpersonnel 212 from which the event alert message(s) originated, radiocommunications device 262 and/or equivalent device for field personnel212, mobile device with broadband data 258 (e.g., smartphone PPT talkgroup or emergency voice channel) and/or equivalent device for fieldpersonnel 212. Once bridged, multiple personnel, invited to theautomatically-triggered communications session may both view the videodata streamed from body-worn camera 254 and/or body-worn camera 255 andhave real time voice communications with field personnel 208 and/orfield personnel 212 from which the event alert message(s) originated.For example, personnel using radio system 234 for voice communicationsmay view the video data streamed from body-worn camera 254 on a GUI ofIWS 220 and speak to field personnel 208 via their radio communicationsdevice. The same would also apply to equivalent devices associated fieldpersonnel 212.

Other media and/or communications resources may be bridged viapre-determined assignment or dynamic determination. For example, adynamic rule may result in a body-worn camera and a radio communicationsdevice of other field personnel in proximity to field personnel 208,being bridged into the biosensor-triggered multimedia collaborationsession. Method 300B returns to step 310.

Returning to step 345, IWS 242 receives an invitation from IWS 220 tojoin the biosensor-triggered multimedia collaboration session. IWS 242determines whether to join and bridge resources that IWS 242 controls tothe session. Method 300B proceeds to step 350.

At step 350, IWS 242 electronically transmits an acceptance to join andmay bridge other communication system 244 to the biosensor-triggeredmultimedia collaboration session after joining the session. IWS 242 maydecline the invitation and method 400 ends. Method 300B proceeds to step365.

At step 365, IWS 220 receives the acceptance from IWS 242 (and/or AgencyB 206) and adds IWS 242 (and/or Agency B 206) to the biosensor-triggeredmultimedia collaboration session. Method 300B returns to step 310.

Returning to step 355, Agency B 206 receives an invitation to join thebiosensor-triggered multimedia collaboration session from IWS 220. Forexample, at substantially the same time or after the initiation of thebiosensor-triggered multimedia collaboration session, incidentmanagement module 224 electronically transmits command messages toinvite IWSs from other partner agencies (e.g., Agency B 206) with whomsecure communications have been established. An example of dynamicaccess among secure communities is described in the EnclavedApplication. The invitation may be automatically transmitted. In anembodiment, the invitation may be presented in the form of a visualsuggestion on a GUI of IWS 220, coupled with a user selectable item toselectively invite the suggested agency resource or alternatively, toselectively exclude a suggested agency resource. Agency B 206 determineswhether to join and bridge resources that Agency B 206 controls to thesession. Once bridged, multiple personnel, from Agencies A 202 and B 206invited to the automatically-triggered communications session may bothview the video data streamed from body-worn camera 254 and/or body-worncamera 255, and have real time voice communications with field personnel208 and/or field personnel 212 associated with originated event alertmessage(s). Method 300B proceeds to step 360.

At step 360, Agency B 206 electronically transmits an acceptance to joinand may bridge the resources that Agency B 206 controls after joiningthe session. Method 300B returns to step 365.

Returning to step 315, when monitoring module 256 determines that anevent is not detected, method 300B proceeds to step 317.

At step 317, a determination is made whether body-worn camera 254(and/or body-worn camera 255) were previously activated (e.g., body-worncamera 254 and/or body-worn camera 255 are recording). When body-worncamera 254 (and/or body-worn camera 255) were not previously activated,method 300B returns to step 310. When body-worn camera 254 (and/orbody-worn camera 255) were previously activated, monitoring module 256electronically transmits a control message via PAN 250 (and/or PAN 251)to body-worn camera 254 (and/or body-worn camera 255) to stop recording.In addition, monitoring module 256 electronically transmits anevent-ended message to IWS 220 at substantially the same time. Method300B proceeds to step 370 and step 375.

At step 370, body-worn camera 254 (and/or body-worn camera 255) receivesthe control message and stops recording data. Method 300B ends.

Proceeding to step 375, IWS 220 electronically receives the event-endedmessage and determines based on static and/or dynamic rules whether tocease the biosensor-triggered multimedia collaboration session. When IWS220 determines to continue the biosensor-triggered multimediacollaboration session, method 300B returns to step 310. For example,more than one event alert may have been received and more than onebody-worn camera is active. When body-worn camera 254 stops recording,other body-worn cameras (e.g., body-worn camera 255), media devices,and/or communications devices may be actively engaged in thebiosensor-triggered multimedia collaboration session. When IWS 220 hasnot received an event-ended message associated with each event alert,method 300B returns to step 310. When IWS 220 has electronicallyreceived an event-ended message associated with each event alert, method300 B proceeds to step 385.

At step 385, IWS 220 ends the biosensor-triggered multimediacollaboration session and method 300B ends.

Mobile Ad-Hoc Radio Based Linked Extensible (MARBLE) System

For any PAN, device, or subject having a radio based communicationdevice capable of send or receiving data, there may exist one or moreportable mesh-capable radio transceiver devices that may be distributedin the field by an operator in the form of a ball, puck or other shapedenclosure that may be held by a human hand and thrown, tossed or placedin the field (e.g., a MARBLE unit or system). A MARBLE unit may be worn(e.g., in a pocket) and perform the functions of personal wearablemicro-server 261. A MARBLE unit may also include interoperabilitygateway functions and perform the functions of personal wearablemicro-server 260 as described above.

FIG. 5 illustrates deployment 500 of a mobile ad-hoc radio-based linkedextensible (MARBLE) system according to an embodiment. The form factorenables a field user to carry and deploy wireless transceiver units(e.g., 560-565) by throwing, dropping and placing them into the field inan area to create a local area ad hoc network 510 similar to local adhoc mesh network 210. A MARBLE system's advantages include the abilityfor a field operator to carry units that are self-contained, do notrequire pre-existing infrastructure or affixing apparatus, and theability to deploy them into the environment in places which may not beeasily accessible. For example, for responders entering a building withlimited radio coverage, it is possible to deploy MARBLE systems as an adhoc network by dropping or throwing MARBLE units on various floors of abuilding as they proceed through the building, thereby ensuringconnectivity. Further, MARBLE units may also be inconspicuous objectswhich can placed or hidden in an environment for stealth surveillance,monitoring and communication.

There may exist a software module coupled to each MARBLE unit thatexchanges administrative messages designating one or more MARBLE unitswhich have interoperability gateway functions and thus have wide areacommunications connectivity to administrative module 222 or a wide areadata communications network (e.g., IP network 204) to serve as a relaygateway for other MARBLE units coupled to a local area ad hoc network(e.g., local ad hoc mesh network 510 which is substantially the same aslocal ad hoc mesh network 210). Designation of a MARBLE unit as a relaygateway (e.g., MARBLE unit 560) may be dynamically assigned based uponrules and parameters including but not limited to a signal strength, aprocessor speed, a bandwidth throughput, a relative number oftransmission links to peer MARBLE units, or a battery power. Further,when mesh connected, devices associated with the relay gateway (e.g.,MARBLE unit 560 similar to personal wearable micro-server 260) mayelectronically, transmit, receive, or store threshold parameters of oneor more devices associated with a second MARBLE unit (e.g., MARBLE unit565 which is substantially similar to personal wearable micro-server 261that is carried or worn by field personnel 212). For example, anequivalent monitoring module 256 associated with MARBLE unit 560 mayperform one or more functions in substitution for an equivalentmonitoring module 257 associated with MARBLE unit 565 based upon certainparameters such as an application or device failure or low power sourcecondition.

FIG. 6 illustrates a system 600 for a MARBLE unit according to anembodiment. A MARBLE system includes an enclosure 660, a digital radiotransceiver 670, a computer processor 620 including but not limited to asystem on a chip (SOC) or an embedded computer, an internal power source630, an antenna 690, a propulsion module 640, a memory 665, a camouflagemodule 680, and GPS 650. A MARBLE system includes software applicationthat enables ad hoc mesh network communications with other MARBLEsystems and other compatible radio transceiver enabled devices that maybe coupled to a MARBLE system.

Other MARBLE unit design features follow.

Enclosure Material. A MARBLE enclosure may be made of rubber, metal, ormaterials that are optimized for various environments and uses. Theseinclude temperature resistance and fire resistance, heat dissipation,chemical and radiological resistant materials, pierce, crush, and impactresistance materials, either alone or in combination with others, inlayers or in disposition. MARBLE systems may also be constructed orcoated with a malleable material that may be shaped in the field such aspolymer materials.

Vents and Heat Dissipation. A MARBLE Unit may have air convection ventsenabling airflow between the interior and ambient exterior environment,or may have heat sinks and fins for heat transfer and radiation to theexterior ambient environment.

Self-Destruct Components. A MARBLE system may contain one or morecomponents enabling the automatic and/or event triggered destruction ofitself and other MARBLE systems. Components may include a softwaremodule which has a time based trigger, a tampering sensor or otherevent-based trigger mechanism that electronically transmits aself-destruction command to the computer processing module for asoftware self-destruction (e.g., to randomize the computer memory,execute malicious code which interferes with the execution of thecomputer bios, operating system kernel and/or applications thereon), oractivates a trigger mechanism which initiates physical destruction ofthe MARBLE Unit, such as a thermite or other explosive discharge. Adestruct message may also be remotely triggered via message receivedover a communications channel between the MARBLE Unit and anthercomputer application.

Ports. A MARBLE Unit may contain ports which are exposed to the exteriorsurface. They may be communications ports such as USB, Ethernet orserial ports, and/or power ports such as AC or DC power connectionports. Ports may also be contained within a MARBLE Unit and may beaccessed by opening a MARBLE unit through a removable or hinged accessdoor or port area, or by opening the entire unit at an accessible seamor junction point.

Power Collection. MARBLE units may have photovoltaic materials affixedor part of the exterior surface material. These cells may be connectedto rechargeable battery components located within the MARBLE Unit.

Shapes. MARBLE units may be of any shape including spheres, rectangles,squares, cones or any other three dimensional shape.

Self-Propulsion and Alignment. MARBLE Units may contain self-propulsioncapabilities such as an electric motor powering an interior or exteriortrack mechanism, exterior wheels, legs or other mechanical elements, orrotator blades enabling the MARBLE Units to move upon or over the groundto a desired location and/or adjust a position. The MARBLE units maycontain a navigation and control module that enables a MARBLE Unit toexecute a plan of movement to a location, and to determine desiredlocation in relation to other MARBLE units. This may be accomplishedusing rules and parameters based upon the location of other MARBLEunits, and the relative signal strength or data connection qualitybetween or among other MARBLE Units. Factors which may be consideredinclude proximity to field-user based devices or other MARBLES, radiosignal strength, environmental interference, quality of service measuredby bit error rate, a unit's actual or relative power levels, processerload, memory, temperature and other factors.

In an embodiment, computer processor 620 (e.g., one or more processors)electronically receives a propulsion message, determines the desiredlocation in relation to the one or more portable mesh-capable radiotransceiver systems, determines a plan of movement to the desiredlocation, and electronically executes the plan of movement using theself-propulsion component. In an embodiment, plan of movement isdetermined based on a rule and a parameter including at least one of: alocation of the one or more portable mesh-capable radio transceiversystems, a relative signal strength of the portable system, a relativesignal strength of one of the one or more portable mesh-capable radiotransceiver systems, a proximity to a device associated with afield-user, a proximity to one of the one or more portable mesh-capableradio transceiver systems, a radio signal strength, an environmentalinterference, a quality of service, a power level, a processor load, amemory, a temperature, or another factor.

Camouflage. A MARBLE unit may camouflage itself using one or more camerasensors coupled to a software module (e.g., camouflage 680) whichcomputer processor 620 uses to interprets colors, brightness andpatterns in its immediate vicinity based upon photo information inputsfrom a camera sensor. The exterior of a MARBLE unit may have lightemitting diode materials applied, embedded or part of its exterior, suchorganic light emitting diodes (OLEDs). Based upon the interpretedvicinity data, computer processor 620 may send control signals to theLEDs to display a color, pattern and brightness corresponding with theinterpreted vicinity data. For example, if a MARBLE is located in greengrass, the camera would capture an image of the grass in its view, sendthe image data to the software module used by computer processor 620 tointerpret colors, patterns and brightness of the image data, create athree dimensional image file of the MARBLE unit's shape and create anapplied exterior image file. In an embodiment, computer processor 620would then send control messages to the exterior LEDs to display theexterior image file periodically, intermittently, or on request. Asbrightness, color or patterns from the environment change, the computermodule would interpret the new environmental data obtained for thecamera sensor and adjust the exterior pattern file and then send newcommands to the LEDs to change to the new exterior pattern.

Means of Camouflage: Using paired camera sensor and LEDs for viewcorrespondent camouflaged display. FIG. 7A illustrates an example 700Aof sensor pairing according to an embodiment. For any three dimensionalobject there exists a point A on the surface of the object X whichcorresponds to a point B on a line segment on the opposite side of theobject X. This imaginary line segment may be extended in one directionto a point A′ which corresponds with a vantage point, and to anotherpoint B′ on another object Y on the other side of the subject object.

If a Camera sensor is located at Point B and is aimed in the same lineof path established in the line segment A′ to A, then the image fromCamera sensor B will be the same as if viewer A′ were looking at PointB′ and when Object X was not present and obscuring Point B′.

By locating LEDs in an area centered on Point A and relating them to theview field of a Camera sensor at Point B, a software module can processimages generated by the Camera sensor B, and then using such imageinformation, modify such image information to proportionately adjustsuch image to take account of the surface shape at Point A and sendcontrol signals to the LEDs in the area centered on Point A to displaysuch image.

In this manner, the image displayed by the LEDs in the area of Point Awill appear to a viewer at A′ as the image of B′, as if Object X was notblocking the view of B′.

In an embodiment, computer processor 620 electronically receives animage data from a first camera sensor (e.g., at Point B) of the one ormore camera sensors based on a first local vicinity (e.g., Point B′),electronically interprets at least one of a color, a pattern, or abrightness of the image data, creates an exterior image file using athree dimensional shape of the portable system and the interpreted imagedata, and electronically transmits the exterior image file to the LEDmaterial, where the LED material presents an exterior image to acorresponding portion of the exterior of the portable system (e.g., LEDsin an area centered on Point A).

In another embodiment, the first local vicinity (e.g., Point B′) and thecorresponding portion of the exterior of the portable system (e.g.,Point A) are collinear points on an imaginary line that extends throughthe portable system, where the first camera sensor (e.g., at Point B) isa collinear point on the imaginary line between the first local vicinity(e.g., Point B′) and the corresponding portion (e.g., Point A).

Offset camera sensor pairing. FIG. 7B illustrates an example of offsetsensor pairing according to an embodiment. The system 700B above canemploy many camera sensors and correspondent LEDs. A camera sensor maybe located in an offset position (e.g., Point C) from a line of viewsegment such as segment AB, where the lens of the camera sensor may beoriented in a line of view which intersects an object which is proximateto B′. This may be done in cases where the camera sensor lens at Point Bcollinear to the imaginary line AB′ is obscured from a view by darknessor close proximity to an object (e.g., the ground or a different object)such that the camera sensor lens cannot focus. In an embodiment, acamera sensor at an offset point, Point C, close to Point B, that iscollinear to the imaginary line AC′ provides an approximate image as ifviewer A′ were looking at Point B′ and when Object X was not present andobscuring Point B′.

In an embodiment where the first camera sensor (e.g., at Point B) isobscured, computer processor 620 (e.g., one or more processors)electronically receives a second image data from a second camera sensor(e.g., at Point C) of the one or more camera sensors, where the secondcamera sensor is offset from the first camera sensor (e.g., at Point B),where the second camera sensor is based on a second local vicinity(e.g., Point C′), and where the second camera sensor is collinear withand between the second local vicinity (e.g., Point C′) and thecorresponding portion (e.g., Point A). Computer processor 620electronically interprets at least one of a color, a pattern, or abrightness of the second image data, creates a second exterior imagefile using a three dimensional shape of the portable system and theinterpreted second image data, and electronically transmits the secondexterior image file to the LED material, wherein the LED materialpresents a second exterior image to the corresponding portion (e.g.,LEDs in an area centered on Point A).

Changing Exterior Color and Patterns by Remote Control. A MARBLE Unitmay be coupled to a software module which can execute commands to changethe color, pattern and frequency of change of a MARBLE Unit. Thesechanges may be executed programmatically according to pre-programmedrules or manually by an operator through a user interface to thesoftware module. For example, a MARBLE Unit may be camouflage mode, andan operator may execute a command to change the color pattern to anorange flashing strobe for the purpose of signifying its location to ahuman. This function may also be executed for two or more MARBLE unit inconcert to create a pattern where they are assigned varied colors toassist in evacuation, or synchronized patterns to provide humaninterpretable context information.

System Implementation

Various aspects of the invention can be implemented by software,firmware, hardware, or a combination thereof. FIG. 8 illustrates anexample system 800 in which the present invention, or portions thereof,can be implemented as computer-readable code and/or text-readable code.After reading this description, it will become apparent to a personskilled in the relevant art how to implement the invention using othersystems and/or processing architectures.

Computer 800 includes one or more processors (also called centralprocessing units, or CPUs), such as processor 810. Processor 810 isconnected to communication bus 820. Computer 800 also includes a main orprimary memory 830, preferably random access memory (RAM). Primarymemory 830 has stored therein control logic (computer software), anddata.

Computer 800 may also include one or more secondary storage devices 840.Secondary storage devices 840 include, for example, hard disk drive 850and/or removable storage device or drive 860. Removable storage drive860 represents a floppy disk drive, a magnetic tape drive, a compactdisk drive, an optical storage device, tape backup, ZIP drive, JAZZdrive, etc.

Removable storage drive 860 interacts with removable storage unit 870.As will be appreciated, removable storage unit 860 includes a computerusable or readable storage medium having stored therein computersoftware (control logic) and/or data. Removable storage drive 860 readsfrom and/or writes to the removable storage unit 870 in a well-knownmanner.

Removable storage unit 870, also called a program storage device or acomputer program product, represents a floppy disk, magnetic tape,compact disk, optical storage disk, ZIP disk, JAZZ disk/tape, or anyother computer data storage device. Program storage devices or computerprogram products also include any device in which computer programs canbe stored, such as hard drives, ROM or memory cards, etc.

In an embodiment, the present invention is directed to computer programproducts or program storage devices having software that enablescomputer 800, or multiple computer 800 s to perform any combination ofthe functions described herein.

Computer programs (also called computer control logic) are stored inmain memory 830 and/or the secondary storage devices 840. Such computerprograms, when executed, direct computer 800 to perform the functions ofthe present invention as discussed herein. In particular, the computerprograms, when executed, enable processor 810 to perform the functionsof the present invention. Accordingly, such computer programs representcontrollers of the computer 800.

Computer 800 also includes input/output/display devices 880, such asmonitors, keyboards, pointing devices, etc.

Computer 800 further includes a communication or network interface 890.Network interface 890 enables computer 800 to communicate with remotedevices. For example, network interface 890 allows computer 800 tocommunicate over communication networks, such as LANs, WANs, theInternet, etc. Network interface 890 may interface with remote sites ornetworks via wired or wireless connections. Computer 800 receives dataand/or computer programs via network interface 890.

Conclusion

The invention can be implemented with software, hardware, and operatingsystem implementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used.

The present invention has been described above with the aid offunctional building blocks illustrating the implementation of specifiedfunctions and relationships thereof. The boundaries of these functionalbuilding blocks have been arbitrarily defined herein for the convenienceof the description. Alternate boundaries can be defined so long as thespecified functions and relationships thereof are appropriatelyperformed.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the invention that others can, by applyingknowledge within the skill of the art, readily modify and/or adapt forvarious applications such specific embodiments, without undueexperimentation, without departing from the general concept of thepresent invention. Therefore, such adaptations and modifications areintended to be within the meaning and range of equivalents of thedisclosed embodiments, based on the teaching and guidance presentedherein. It is to be understood that the phraseology or terminologyherein is for the purpose of description and not of limitation, suchthat the terminology or phraseology of the present specification is tobe interpreted by the skilled artisan in light of the teachings andguidance.

Exemplary embodiments of the present invention have been presented. Theinvention is not limited to these examples. These examples are presentedherein for purposes of illustration, and not limitation. Alternatives(including equivalents, extensions, variations, deviations, etc., ofthose described herein) will be apparent to persons skilled in therelevant art(s) based on the teachings contained herein. Suchalternatives fall within the scope and spirit of the invention.

The breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

What is claimed is:
 1. A personal wearable micro-server system,comprising: a transceiver; one or more processors coupled to thetransceiver; a first camera sensor coupled to the one or moreprocessors; and light emitting diode (LED) material coupled to the oneor more processors, wherein the LED material is coupled to an exteriorof the personal wearable micro-server system, and wherein the one ormore processors are configured to: receive first image data via thefirst camera sensor based on a first local vicinity; present a firstimage on the exterior via the LED material based at least on the firstimage data, wherein the first local vicinity and a corresponding portionof the first image on the exterior are collinear points on an imaginaryline that extends through the personal wearable micro-server system;receive a wireless signal via the transceiver; and present a secondimage on the exterior via the LED material based at least on thewireless signal.
 2. The personal wearable micro-server system of claim1, wherein the first camera sensor is obscured, the one or moreprocessors are further configured to: receive second image data via asecond camera sensor wherein the second camera sensor is offset from thefirst camera sensor, wherein the second image data is based on a secondlocal vicinity, and wherein the second local vicinity is collinear withthe first image on the exterior; and present a third image on theexterior via the LED material based at least on the second image data.3. The personal wearable micro-server system of claim 1, wherein thesecond image comprises a change in at least one of: a color, a pattern,or a frequency of change of the exterior.
 4. The personal wearablemicro-server system of claim 1, wherein the one or more processors arefurther configured to: update the exterior based at least on additionalimage data received from the first camera sensor, wherein the additionalimage data is received periodically, intermittently, or on request. 5.The personal wearable micro-server system of claim 1, wherein the one ormore processors are further configured to perform relay gatewayfunctions for a second personal wearable micro-server system.
 6. Thepersonal wearable micro-server system of claim 5, wherein the one ormore processors are further configured to determine to perform the relaygateway functions based on at least one of: a signal strength, aprocessor speed, a bandwidth throughput, or a battery power.
 7. Thepersonal wearable micro-server system of claim 5, wherein the one ormore processors are further configured to determine to perform the relaygateway functions based on at least a relative number of transmissionlinks to peers.
 8. The personal wearable micro-server system of claim 1,further comprising: a self-destruct component coupled to the one or moreprocessors, wherein the one or more processors are further configured toelectronically receive a self-destruct command triggered by at least oneof: a tampering sensor, a time-based trigger, or an event-based trigger.9. The personal wearable micro-server system of claim 8, wherein toinitiate the self-destruct command, the one or more processors arefurther configured to activate a software self-destruct module.
 10. Thepersonal wearable micro-server system of claim 1, further comprising: aself-destruct component coupled to the one or more processors, whereinthe one or more processors are further configured to receive a messagethat triggers a self-destruct command.
 11. The personal wearablemicro-server system of claim 1, further comprising: a self-propulsioncomponent coupled to the one or more processors, wherein the one or moreprocessors are configured to move the personal wearable micro-serversystem to a desired location and adjust a position of the personalwearable micro-server system.
 12. The personal wearable micro-serversystem of claim 11, wherein the self-propulsion component comprises atleast one of: an electric motor, an interior track mechanism, anexterior track mechanism, an exterior wheel, a mechanical leg, a rotorblade, a control module, or a navigation module.
 13. The personalwearable micro-server system of claim 11, wherein the one or moreprocessors are further configured to: receive a propulsion message;determine the desired location in relation to a second personal wearablemicro-server system; and execute a plan of movement using theself-propulsion component.
 14. The personal wearable micro-server systemof claim 13, wherein the plan of movement is based on a rule and aparameter comprising a location of the second personal wearablemicro-server system.
 15. The personal wearable micro-server system ofclaim 13, wherein the plan of movement is based on a rule and aparameter comprising a proximity to the second personal wearablemicro-server system.
 16. The personal wearable micro-server system ofclaim 13, wherein the plan of movement is based on a rule and aparameter comprising a relative signal strength of the second personalwearable micro-server system.
 17. The personal wearable micro-serversystem of claim 13, wherein the plan of movement is based on a rule anda parameter comprising at least one of: an environmental interference, aquality of service, a power level, a processor load, or a temperature.18. The personal wearable micro-server system of claim 1, comprising athree dimensional shape of a sphere, a rectangle, a cone, or a cube. 19.The personal wearable micro-server system of claim 1, wherein theexterior comprises material comprising radiation resistant material. 20.The personal wearable micro-server system of claim 1, wherein theexterior comprises material comprising impact resistant material. 21.The personal wearable micro-server system of claim 1, wherein theexterior comprises material comprising malleable material that may beshaped.
 22. The personal wearable micro-server system of claim 1,wherein the exterior comprises material comprising at least one of:rubber, metal, temperature resistant material, fire resistant material,polymer material, or chemically resistant material.
 23. The personalwearable micro-server system of claim 1, further comprising: a portcoupled to the one or more processors, comprising at least one of: auniversal serial bus (USB) port and a removable cover.
 24. The personalwearable micro-server system of claim 1, further comprising: arechargeable battery component, coupled to the one or more processors,wherein the rechargeable battery component is coupled to a photovoltaicmaterial affixed to the exterior.
 25. A method for a personal wearablemicro-server system, comprising: receiving first image data via a firstcamera sensor of the personal wearable micro-server system based on afirst local vicinity; presenting a first image on an exterior of thepersonal wearable micro-server system via light emitting diode (LED)material coupled to the exterior based at least on the first image data,wherein the first local vicinity and a corresponding portion of thefirst image on the exterior are collinear points on an imaginary linethat extends through the personal wearable micro-server system;receiving a wireless signal via a transceiver; and presenting a secondimage on the exterior based at least on the wireless signal.
 26. Themethod of claim 25, wherein the first camera sensor is obscured, themethod further comprises: receiving second image data via a secondcamera sensor wherein the second camera sensor is offset from the firstcamera sensor, wherein the second image data is based on a second localvicinity, and wherein the second local vicinity is collinear with thefirst image on the exterior; and presenting a third image on theexterior via the LED material based at least on the second image data.27. The method of claim 25, further comprising: receiving a propulsionmessage; determining a desired location in relation to a second personalwearable micro-server system; and executing a plan of movement using aself-propulsion component of the personal wearable micro-server system.28. The method of claim 27, wherein the plan of movement is based on arule and a parameter including a location of the second personalwearable micro-server system.
 29. The method of claim 25, furthercomprising: receiving a self-destruct command; and activating physicaldestruction of the personal wearable micro-server system based at leaston the self-destruct command.
 30. The method of claim 25, furthercomprising: determining a desired location in relation to a secondpersonal wearable micro-server system; and executing a plan of movementto the desired location.
 31. The method of claim 30, wherein the plan ofmovement is based on a relative signal strength of the second personalwearable micro-server system.
 32. A non-transitory computer-readablemedium storing instructions that, when executed by a processor of apersonal wearable micro-server system, cause the personal wearablemicro-server system to perform operations, the operations comprising:receiving first image data via a first camera sensor of the personalwearable micro-server system based on a local vicinity; presenting afirst image on an exterior of the personal wearable micro-server systemvia light emitting diode (LED) material coupled to the exterior based atleast on the first image data; receiving a wireless signal via atransceiver; presenting a second image on the exterior based at least onthe wireless signal; moving the personal wearable micro-server system toa desired location; and adjusting a position of the personal wearablemicro-server system.
 33. The non-transitory computer-readable medium ofclaim 32, wherein the first local vicinity and a corresponding portionof the first image on the exterior are collinear points on an imaginaryline that extends through the personal wearable micro-server system. 34.The non-transitory computer-readable medium of claim 32, wherein thefirst camera sensor is obscured, the operations further comprising:receiving second image data via a second camera sensor wherein thesecond camera sensor is offset from the first camera sensor, wherein thesecond image data is based on a second local vicinity, and wherein thesecond local vicinity is collinear with the first image on the exterior;and presenting a third image on the exterior via the LED material basedat least on the second image data.
 35. The non-transitorycomputer-readable medium of claim 32, wherein the operations furthercomprise: determining to perform relay gateway functions based at leaston a relative number of transmission links to peers; and performing therelay gateway functions for a second personal wearable micro-serversystem.